Can no longer "revise contents" on public folder post
Suddenlyour users are reporting they can no longer double click on apublic folder posting,from the menu pane choose Edit then revise contents. The revise contents selection is completely greyed out. Any ideas on what would cause this or how to fix?Owners of the public folders report this issueMicrosoftExchange 2003 SP2
January 6th, 2009 9:19pm

Issue description: Users cant use the Revise Contents button to modify the posts in the public folder Check info: 1. Whether the issue happens on single public folder or all public folders? 2. Does the issue occur on all users when they access the posts? 3. Does the issue persist on the owner of the public folders? 4. If user creates a new post in the public folder now, will the Revise Contents button work for it? 5. Did you set item-level permission for the posts in the public folder? The permission for Revise Contents: "Editor" can revise anything "Author" can revise their own works "Reviewer" can only read but not revise Troubleshooting: 1. Please base on the list above to check the permission for users by using PFDavAdmin a. Launch tool on client [Install NET Framework 1.1 at first] b. File menu->connect->set the parameters->OK c. Right-click problematic folder->Folder permissions d. Check the permission on users 2. Please still use PFDavAdmin, lets check the DACL state, and item-level permission a. Right-click problematic folder->Check DACL state->OK b. See if it displays DACL is good for the problematic folder and the subfolders under it c. Right-click problematic folder->Check for item-level permissions->select The selected folder and all subfolders option, and click OK d. Please post the output for analyzing 3. Please try to reproduce the issue with a fresh new outlook profile on a testing PC
Free Windows Admin Tool Kit Click here and download it now
January 7th, 2009 12:53pm

This issue happens on all public folders and all users seem to be affected. This affects all users on the folders including owners. New folders also have this issue. All folders have item level permissions. Here is the output for item level permissions Public Folders\Group\International\Messaging Test Checking for item-level permissions... Found 0 total items. Found 0 items with item-level permissions. Found 0 items whose security descriptors could not be read. I will try to reproduce the issue with a fresh outlook profile tomorrow. Thanks for your ideas!!
January 12th, 2009 7:01am

Please also compare public folder related permissions with mine in the AD by using ADSIEditor: a. Launch ADSIEditor b. Expand Configuration container->CN=Configuration,DC=DomainName,DC=com->CN=Services->CN=Microsoft Exchange->CN=OrganizationName->CN=Administrative Groups->CN= AdministrativeGroupName->CN=Servers->CN=ServerNameOfPublicServer->CN=InformationStore->CN=StorageGroupName c. Double-click the CN=PublicStoreName in the right-pane d. In the Security tab, please check the permissions Anonymous Logon: Read, Create named properties in the information store, Special Permissions Everyone: Same as Anonymous Logon group e. Expand Configuration->CN= Configuration,DC=DomainName,DC=Com->CN=Services->CN=Microsoft Exchange->CN=OrgName->CN=Exchange Administrative Group (xxx)->CN=Folder Hierarchies f. Double-click CN=Public Folders in the right-pane g. In the Security tab, please check the permissions Anonymous Logon: Create named properties in the information store, Create Public Folder Everyone: Create named properties in the information store, Create Public Folder, Special Permissions
Free Windows Admin Tool Kit Click here and download it now
January 12th, 2009 7:35am

I created a new outlook profile on a different machine and I still have the same issue.Here are the answers to your other questions.For d. Security tab setting = Anonymous and Everyone both have Read, Create named properties in the information store, special permissionsFor f. Security tab setting = Anonymous Logon = Create named properties in the information store, create public folder, special permissionsEveryone = Create named properties in the information store, create public folder, special permissions
January 13th, 2009 10:39pm

For f. you have Special Permissions on Anonymous Logon? It shows unchecked in all my exchange 2003 labs. My environment is exchange 2003 SP2. Please backup the latest system state at first, and try to uncheck the Special Permissions Does the issue only persist on one public store server, or you only have one public store server? Please try to create a new storage group and a new public store in it, see if the issue still occurs. If not, try to compare permissions in Security tab both on the folders and the entries in them between the newly created and the olds with ADSIEditor
Free Windows Admin Tool Kit Click here and download it now
January 14th, 2009 6:04am

I have a test domain I can try this in. We have 11 public folder servers all of which are Exchange 2003 SP2 but I have not tested content from each and every one. I have randomly selected folders and this is occurring on every single one of them. We are in a mixed environment and have migrated most mailboxes to Exchange 2007. I suspect the Exchange 2007 schema may have a part in this but I am not positive. Thank you for your time and insight.
January 14th, 2009 6:21am

This ended up being a problem with Outlook and specifically the file outcmd.dat. After deleting this and allowing Outlook to recreate the problem went away. Kind of frustrating!
Free Windows Admin Tool Kit Click here and download it now
March 4th, 2009 7:48pm

Hoosie2 said: This ended up being a problem with Outlook and specifically the file outcmd.dat. After deleting this and allowing Outlook to recreate the problem went away. Kind of frustrating!We're seeing the same thing here only the problem comes back after a couple of weeks so we have to keep deleting the outcmd.dat file. Can someone explain why that file affects the Revise Contents menu option and is there a better solution than deleting the outcmd.dat file every few weeks? Thanks!
March 12th, 2009 12:42am

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics